LOGIC 2000 February/LogicCd--feb.2000-mac-cdr.iso/Apple II/TWOQWKV2.03/DOCS.V2.01

Text File | 1996-01-13 | 30KB | 803 lines

                    _________________________________________

                      2qwk! 2.01 (c) 1996 lysergic software
                    _________________________________________


Table of contents

Introduction............................0.00
Installation............................1.00
Preferences.............................2.00
   archiver.............................2.10
   directories..........................2.20
   general..............................2.30
   replies..............................2.40
   hardware.............................2.50
Using the program.......................3.00
Archiver................................3.10
Messages................................4.00
Editor..................................5.00
Utilities...............................6.00
Miscellaneous...........................7.00
Appendixes..............................8.00
   troubleshooting......................8.01
   sourcecode...........................8.02
   fanmail..............................8.03


0.00    Introduction

0.01    About the documentation

  Writing documentation sucks, which is why I've foisted much of the duties
  off onto Mushroom.  [Coding sucks, which is why I let Tom do it. -m3]

  Throughout the document I've used some 'typographical aids' to highlight
  information in the text:

   - a :?: following the text indicates a helpful hint.

   - a :!: indicates a helpful warning.

0.02    About the 2qwk!

  The 2qwk is an offline mail reader for qwk mail systems. An offline reader
  (olr) allows the user to download new messages and mail in a compact format
  and read and reply to them offline. You save time and connection charges
  by downloading a mail packet and logging off in a fraction of the time it
  would take to read and reply to messages online.

  The program is now written in assembly language using a custom API to do
  some of the grunt work that macos was used for in previous versions. This
  results in a small, fast and efficient package that is sweet and slippery,
  like a sheriff's bare red ass.


1.00    Installation

1.01    The archive

  I've decided to skip the Zip archiver since the extra step was apparently
  more than some people could take. If this is the first time you've used
  the 2qwk you'll need to use the qfix program to modify your system files
  to allow ms-dos filenames.  And there's no way around patching your system
  files to use the 2qwk (trust me, it's safe) so don't even ask.

1.02    The qfix

  New with 2qwk 2.0 is quickfix. To patch the system files on your boot
  device (named in this example) '/gopshill' you would do:

   'qfix /gopshill/system' (if run from a shell environment)

   or if not running from a shell environment like Davex:

   'qfix' (wait for the prompt, then) '/gopshill/system'

  Read the qfix documentation for a better understanding of this swell new
  program (and how to patch your other files).

1.03    The install

  After you've unpacked all the archive files, you need to run the Install
  program to initially configure the 2qwk. This does some one-time stuff and
  can be deleted after it has run. It automatically launches the 2qwk after
  it's finished.

  :!:  The install program checks to see if'n prodos has been patched (and
       it don't work if it hasn't).  Use qfix before trying to install!

  :?:  Some people have had problems in the past with the name of the program
       (2qwk!) when working with old programs that don't let the file system
       do its job and determine if a filename is valid. To this end you can
       now rename the 2qwk! file to whatever you like after the installation.

1.04    The required external programs

  You'll need a program to extract the zip archives that the qwk packet is
  made of. Either Angel .81b or PMPUnzip 2.0 will work.

  :?: The 2qwk is set up to run the archiver (see section 2.10) when you
      select Archiver from the main menu. When you exit the archiver it
      will return to the 2qwk.

  :!: Angel needs to be patched to keep it from sanitizing filenames. You
      can use qfix to do this:

       'qfix /gopshill/archivers/angel.system'

1.05    Modified Angel  (qfix's ANGLE patch)

 In addition to not sanitizing filenames, it is possible to modify Angel to
 be a bit more 2qwk friendly. You should use qfix your angel.system file with:

       'qfix /gopshill/archivers/angle'

 This will do the following:

  - Skip the splash screen (Cmd-? is disabled).

  - Preset the source (rep) and destination (qwk) directories.

  - Allow Cmd-Rtn to process all the files in the archive and automatically
    exit back to the 2qwk (Cmd-Down is removed).

 The best way to utilize this is to have a single transfer directory that you
 use for uploads and downloads. Set your Rep directory (see section 2.22) to
 this. When you launch the archiver from 2qwk, the pathnames are set so all
 you have to do is open the qwk packet, press Cmd-Rtn, and when it is done
 unpacking it will exit back to the 2qwk and the packet will be loaded.

 :?: This is unauthorized, but I figure it betters two years of nothing :).

1.06    System requirements

 You need at least a 128k enhanced //e (or equivalent) running ProDOS 8
 2.0.x that has been enhanced to allow ms-dos filenames (via quickfix).


2.00    Preferences

 After you have installed and run the program, you will probably want to
 set your personal preferences. To do this, use the arrow keys to move the
 highlight bar to the 'preferences' command and press the return key.

 :?: You select commands in the program by using the arrow keys or the
     keypad to highlight the command and press return. You can also usually
     enter the first letter of the command to directly execute that command.

2.10    Archiver

 The 2qwk can launch your favorite archiver for you from the main menu;
 this is where you enter the pathname and filename information.

2.20    Directories

 This command lets you set the pathnames that the program will use to locate
 specific files.  If you do not specify a path, the 2qwk program path
 defined by the install will be used.

 :?: If you're using floppies you might want to set these directories to
     another (ram?) disk.

 :?: Shortcut prefixes are available!  To access any files in a given path,
     you can use the character instead of the full pathname (e.g. 1/welcome).

      @/  represents the 2qwk /data subdirectory
      1/  represents the qwk directory (see 2.21)
      2/  represents the rep directory (see 2.22)

 :!: All files used by the 2qwk now reside in the /data subdirectory. These
     include iiqwk.tag, iiqwk.sig, launch.lst, picklists, whatever.

2.21    QWK directory        | ../qwk/

 This is where 2qwk expects to find the contents of the QWK packet that you
 have downloaded.

 :!: You may use a RAM disk as the qwk directory if you have more than 128k
     of RAM but no hard drive, or if you prefer lotsa speed and volatility.

2.22    REP directory        | ../rep/

 This is where the program stores the replies that you have written. When you
 exit the program, the replies are "stored" in 'bbsid.rep', a zip-compatible
 archive. If you quit the program and choose to save your replies, it will also
 contain BBSID.MSG.

 :?: The bbsid parameter is an identifying token chosen by the host that you
     picked up the packet from.

 :?: You might want to set this directory to your term program's default upload
     directory (recommended).

2.30    General

 These options apply to either those functions that apply throughout the entire
 program, or those that don't fit elsewhere.

2.31    Blink rate      | (varies)

 The 2qwk now uses a flashing cursor when entering text; this sets the speed
 at which it flashes. A larger number indicates a longer delay.

 :?: The install program attempts to set the number based on your machine type
     and whether you have a twgs or not. Try MHz x 8.

2.32    Index           | long

 The message selection dialog can either show a short index (subject, date,
 and time) or a long index (subject, from, and to).

 :?: You can toggle this (for this session) by hitting '-' in the message
     selection dialog.

2.33    Load type       | overstrike

 When importing text from disk (section 5.01), you can either have the stuff
 overwrite what is in the editor below the cursor (if anything) or be inserted
 at that point, moving everything below the cursor down. Whichever you choose
 here, you can do the opposite when importing by holding down the Command key
 while the text loads, so pick what you think you'll do most often here.

 :?: Due to the way the editor is designed inserting text into the middle of
     a long file can be painfully slow. You have been warned.

2.34    Support qwke    | on

 This enables the program to support addresses (to:) and subjects that are
 longer than 25 characters. If you never read messages from a qwke compliant
 host or internet-style headers you should turn this off.

2.40    Replies

 The replies command will let you change aspects of the program that relate
 to replying to (or entering) messages.

2.41    Add initials    | on

 This command will toggle whether or not the program will show the initials
 of the person you're quoting. "SS> Hello". Like that.

 :?: This helps to identify who the text is from and the alternative is a bare
     reply character, ">".

2.42    Fido compliant  | on

 This determines whether the program uses fido compliant taglines or not,
 it's usually a good idea anyway.

2.43    Message header  | on

 When this setting is on, the program will add a small header to the beginning
 of your reply.

 :?: If you hold down the command (open-apple) key while selecting this option
     you will be able to edit the message header string. You can use any text
     you like, along with these variables:

      @@a  address of message sender (see below).
      @@d  date the message was written (01-01-95).
      @@f  who the message was written by.
      @@l  alternate date format (Jan 01, 1995).
      @@m  carriage return (see below).
      @@p  aligns the second line of a tagline.
      @@s  subject of the message.
      @@t  who the message was written to.
      @@1  first name of message sender.

     The default string is "Hello @@1,@@m@@mOn @@d, @@f writes to @@t:" which
     when it reads the header "from: Earl Wade" renders something like:

        Hello Earl,

        On 07-04-95, Earl Wade writes to All:

     You may have to do some tweaking in the message if you are reading an
     Internet conference ("Hello [e-mail], ...").

 :?: You can be artistic with @@m; you can create Bill The Cat by using the
     string (without the quote-marks): "_   /|@mm\'o.O'@mm=(___)=@mm   U".

 :?: @@a will take the address from qwke (qwke must be on in Preferences);
     if there ain't no address or qwke is turned off, it will print the name
     from the qwk header.  If you use a reply header of '@@a wrote:' and turn
     off the initials it will format the reply similar to what your average
     newsreader gives.

2.44    Quoting style   | reply-character

 There are three basic styles of quoting. As you might imagine, 'none' turns
 off quoting. The 'raw-text' mode puts the text in the editor more or less as
 it is in the message. The 'reply-character' mode prefaces all text from the
 message with the Fido standard " SS> " deal.

 :?: The editor employs flowyquoting(tm) to ensure that the message text is
     left in a readable state after it has been quoted.

 :?: Command-R will let you change the quoting character. It really should be
     left as '>' though.

2.45    Taglines        | on

 Do you want to use taglines? Sure you do, that's why you're using an offline
 reader!

 :?: The @@ variables (see section 2.43) can also be used in taglines.

 :?: Command-T will let you customize the string that the tagline stealing
     routine uses to rip taglines. The program looks for the four characters
     that are in positions 3-7 on a line.

     * OLX 1.52 * I like spam almost as much as my PC.
       ^^^^

     So you would add 'OLX ' if you wanted to rip OLX tags and it wasn't
     already supported.

2.46    Editor width    | 74

 You can set the right margin in the editor. This is useful for boards which
 have narrow message widths. The default should be sufficient for most boards.

2.50     Hardware

 The 2qwk needs a little more information about your system if you want it
 to print messages or operate a mouse on a non-GS.

2.51     Clock           | on

 This refers to the clock in the upper right corner, not your computer's own
 clock. If you don't like it, turn it off.

 :?: If your clock requires a driver, run it before launching 2qwk.

2.52     Linefeeds       | off

 Not all printers are created equal.  Yours may or may not need the computer
 to throw it linefeeds (lf after cr) to make it advance to the next line.
 Try printing a message, after setting the slot and init string (2.54-2.55),
 and the results should clue you in.

2.53     Mouse           | (varies)

 If the install program detects a mouse card this defaults to on. If you
 would rather not use one you can turn it off. The 2qwk will automatically
 recognise a GS mouse; a mouse on a //e (in slot 4) or a //c will also be
 noticed by the installer.

 :?: If you insert a mouse card in your //e after installation or the mouse
     card is in a different slot than 4, tell the program what slot it is in
     by hitting Command-M.

 :!: Do not meddle with Command-M under any other circumstances or you will
     have to re-install the program completely. If you accidentally typed
     that keystroke and get "slot: 0", hit escape immediately!

2.54     Printer slot    | 0

 If you have a printer, enter the slot the interface card is in here.  If
 you don't, try not to hit "p" while reading a message.

2.55     Printer init string <not shown>

 Your printer may need specific instructions on how to do what you want. Or
 maybe you want to do something special, like boldface everything or print
 in French (on the Imagewriter). Your owner's manual should tell you what
 to do; neither the author of 2qwk! or of the docs knows much about printers.
 You set the init string by hitting Control-P and entering the info. Control
 characters are inputted as ^-whatever (control-I is rendered ^I).

 :?: The generic 80-column printer initialization is "^I80N"


3.00     How to use the program

 Every effort has been made to make this program as easy to use as possible,
 but reading through the rest of the manual can only help.

 Using the mouse is pretty straight-forward. If you put your mouse cursor on
 an item and click on it, it will act as though the item was selected and you
 had pressed return.

3.01    The qwk packet

 Due to the general lack of shell-style archivers (and no desire on my part
 to write one) the program expects you to have already placed the contents of
 a qwk packet into the qwk directory (see 2.21).

 :?: A good compromise around this (what I do anyway) is to use Angel with the
     angle patch (see 1.05). You can also:

     a) Run the 2qwk without extracting the packet.
     b) Hit enter on Archiver to launch your archiver.
     c) Extract the packet.
     d) Exit the archiver (which relaunches 2qwk and loads the packet).

3.02    How to use the menus

 All menus and lists in dialogs are navigated by using the Up and Down arrows
 to highlight the item, and Return to select it. You can also use the keypad.

3.03    How to use dialogs

 All dialogs use Return to accept and Escape to abort. Special dialogs will be
 covered on their own.

3.04    How to use picklists

 A picklist is a <cr> terminated text file that contains items which will be
 commonly used. It is then called by pressing (in a line edit event, such as
 while in the edit file dialog) Option and the file identifier.

        File: @/picklista (Option-A or closed-apple-A)

        [e-mail]
        [e-mail]
        [e-mail]

 This brings up those items in a boxed menu. After you pick the item that you
 wish to use (or escape to not choose any) you proceed with the dialog as if
 you had typed that information in yourself.

 This is useful for email addresses, pathnames, search criteria, taglines or
 whatever you want to use it for.

 :!: There is a limit of 50 items which can contain 2k of data.

3.05    Online help

 An online help system is available in major areas of the program by pressing
 the '?' key. If the title bar contains numbers then the corresponding sub-
 screens may be viewed by pressing that key.

 :?: If you never view the help stuff you can save a few kilobytes by removing
     the @/help file.

3.06    Bulletins

 The nature of bulletins are so generally worthless that I yanked support from
 this release. If anyone can come up with a valid reason (hah!) to have them
 added back, I'll do it.  Same story with News and Files, they're gone.  Also
 missing is the logon/logoff message toggle in Preferences (some boards send
 texts so you can pretend you are online when you are offline, what fun).

3.07    Packing replies

 The active replies are stored in a pkzip compatible archive when you exit the
 program. This could be a lot faster but having to deal with deleted messages
 really slows things down. To keep things exciting, the crc-32 is displayed
 while the replies are being processed.

 :?: The crc32 routine is by Neil Parker.

3.10    Archiver

 This main menu selection will launch the archiver you specified in the
 Preferences (see 2.10). It's the first thing you will want to do when you
 get a new QWK packet if you use the startup method listed in section 1.05.

 :?: If the 2qwk doesn't find the qwk file "control.dat" on startup, you
     will get a dialog box (hit return), and the Archiver option will
     automatically be highlighted. If it does find that file (old or new)
     the Messages option will be highlighted instead.

4.00    Messages

4.10    The conference selection dialog

 This is the dialog you get when you select the messages item from the main
 menu. It displays the first 32 conferences, next to each conference it shows
 how many messages are available.

4.11    Dialog specific commands

        '+'/'-' Move to the next and previous conferences, respectively, with
                messages (also Cmd-Rt & Cmd-Lft)

        'a'     Add conference (if host supports offline configuration).
        'd'     Drop conference
        'e'     Enter a new message in selected conference.

4.12    Special conferences

        Replies         Messages which you have written.
        Personal        Messages addressed to you.

4.20    The message index dialog

  When you select a conference that has messages, the program will display
  this dialog. It shows an index of the first 16 messages with information on
  either the date and time or the author and intended recipient.

4.21    Dialog specific commands

        '-'     Toggle between short and long index (see 2.23)
        '3'     Show next 16 messages (also command-down)
        '9'     Show previous 16 messages (also command-up)

4.22    Additional commands for replies conference

        'c'     send a carbon-copy of this reply.
        'd'     delete (and undelete) this reply.
        'r'     re-edit this reply.

4.22.1   Carbon copy

 You can send carbon copies of replies other people or conferences. If the
 message has qwke routing info (a To: line) you should use 'r' to edit the
 reply and then undelete the original.

4.22.2   Delete/undelete reply

 Useful if you decide you don't want to send a message afterall, or want to
 reanimate a killed message.

4.22.3   Re-edit reply

 Say you came up with the answer you were seeking at the end of a session to
 a question you'd replied to at the beginning of your reading. You don't have
 to send two messages, you can edit the one you've already sent.  This option
 is also helpful if you accidentally saved your reply before you were
 finished writing it (Ctrl-W is close to Ctrl-E, yes?).  This happens a lot.

4.30    Reading messages

 The entire message is loaded into memory allowing you to scroll through the
 message text by using the Up and Down arrow keys. You can move back and forth
 through the messages in a conference by using the Left and Right arrow keys.

 You can also use the mouse. Clicking on the top two lines of the screen will
 scroll up, on the bottom two will scroll down. Clicking on the left side of
 the screen will take you to the previous message and on the right will take
 you to the next message. Click on the message text to exit to the message
 index dialog.

 After you have finished reading all messages in a conference you will exit to
 the conference selection dialog and it will move to the next conference that
 contains messages.

4.31    The export command      (e)

 This command will export the message text to file. If the file exists it will
 append the text to the end of the file.

 :?: If you don't specify the pathname it will save to the directory where
     the 2qwk resides. The special prefixes (see 2.20) also can be used.

4.32    The find command        (f)

 The find function searches through the messages in the conference and will
 display the first that contains the specified text. This is especially useful
 in conferences with lots of traffic. It is not case-sensitive. While you're
 waiting for the program to grind through all the data, a spinning cursor is
 provided to amuse you.

 :?: You can search for more than one item by seperating them with a semi-
     colon. For example 'john;scully;sucks' would find any message that
     contained 'john', 'sculley' or 'sucks'.

4.32    The find next command   (g)

 Use this to find the next iteration of the find sequence without bringing
 the find dialog back up.

4.33    Add user to kill file   (k)

 Sometimes you'll find messages by a dimbulb or just plain take a dislike
 to a particular person and not want to see messages from them. Hey, put
 away that ak-47 and just add them to your kill file. This puts them into
 a file (@/twit.bbsid) that ensures you'll never see another message
 originating from them.  You'll still see replies to the dork, however.

 :?: You can clear the kill file by using K from the main menu. You can
     edit it by using Cmd-K.

4.34    The reply command       (r)

 This brings up the reply dialog. You can press Return to accept the default
 items and move to the editor (see 5.0), or:

4.34.1  Edit reply dialog       (e)

 This allows you to edit:

   Conf: Which conference the message will be posted in.
     To: Who the message will be addressed to.
   Subj: The subject of the message.
   Priv: Should the message be flagged as private (yes) or public (no).
    Tag: Write your own.

4.34.2  New random tagline      (t)

 Picks a new tagline at random.

4.34.3  Next tagline            (right)

 Moves to the next tagline in the file (wraps to 0).

4.34.4  Previous tagline        (left)

 Moves to the previous tagline (wraps at 0).

4.35    Steal tagline           (s)

 Stealing taglines is not an exact science. This is why I've implemented
 tagboy(tm), the configurable tagline stealer. This allows the 2qwk to adapt
 to virtually any other mail readers signature line (see 2.45).

 :?: The tagboy(tm) comes preconfigured to steal taglines for OLX, SLMR, TLX,
     KingQWK, 2qwk!, OFFLINE and those preceded by '...'.

 :?: You can edit the tagline search string (for this session) without going
     to prefs:rep by using Command-T; see 2.45 for what it scans for already.

4.36    Print message           (p)

 Now you can throw the message you're reading to the printer without having
 to export it and print it with another program (unless you want to)!

 :?: Print drivers

     I don't have a printer, or any reference materials for one, so I'm
     using a really generic driver. I'm also providing the commented source
     for the driver so you can write your own, better driver, if you feel
     like it.

 :!: You must have set all the vital data in the prefs:hardware department
     (see 2.5) for this to work. You must also have a printer online, duh.

5.00    The editor

 This editor is based on the blackspring editor that was originally written
 by Ron Mercer (which means that it is memory hungry and line oriented) and
 yes it is on top of my list for things to rewrite.

 :!: Some boards impose size limits to messages (a certain number of lines
     or kilobytes per message), and like the width (see 2.36) you should
     know what a board's limits are before posting messages with 2qwk.

 The commands (command-?) are pretty self-explanatory, but some of the more
 complicated are:

5.01    Importing text          (ctrl-l)

 This imports text at the cursor position. You can drag in binscii's and
 incriminating text from disk at will, where you want it. The setting in
 prefs:general:load type (see 2.33) selects whether imported text overwrites
 or is inserted (forcing everything below the cursor down).

 :?: The text is processed through the flowyquoter for more prettyness.

 :?: You can change how text is imported by holding down the open-apple
     key during loading (does the opposite of the prefs setting).

 :!: The limit on length of imported text, or a message in general, is ~525
     lines.  Text beyond that point will not be loaded into the editor.

5.02    Re-edit reply dialog    (Command-N)

 Lets you go do the stuff listed in 4.34.1 over while in the message editor.
 Handy if you suddenly decide to change the conference number (which happens
 often when you're trying to make a private-email reply to a public-only
 conference), and faster than editing a message you've already saved to the
 Replies conf or bailing out of the message and starting over.

 :?: If you're just editing a text file, this allows you to save it to a
     new filename.

5.03    The signature file      (@/iiqwk.sig)

 If it exists, the editor will append the contents of the signature file onto
 the end of your messages. Create one with the editor (see 7.1) if you dare.

 :?: Use command-w or command-s to avoid adding the signature file.
     Use control-w or control-s to save your message with the signature.


6.00    Utilities

 These are pretty much completely different from previous versions.

6.10    Import taglines

 This allows you to import taglines from <cr> terminated files into your own
 iiqwk.tag file. Treat it like any other dialog (Rtn accepts, Esc aborts) with
 the Down arrow skipping the current tagline. Hold down the command key while
 accepting the tagline to process all remaining taglines automatically.

 :?: By using a set tagline size it drastically speeds up tagline manipulation,
     this might change in future versions but probably not.

6.20    Make ndx files

 This creates the .ndx files (which the 2qwk needs) from the messages.dat file
 in the qwk packet.  If you didn't get .ndx files in your qwk, use this.


7.00    Miscellaneous

7.10    Editing text files      (E from main)

 This command lets you create or edit textfiles.  All the message editor rules
 you've read about so far are in effect here as well.

 :?: You can change the name of the file you're editing by pressing Command-N
     in the editor.

7.20    Launch programs         (L from main)

 This command brings up a list of programs to run. Replies will *not* be
 processed into the bbsid.rep file (because all programs will quit to the
 2qwk when you exit) unless you hold down the Command key while launching.

 :?: You can edit the launch list by using Command-L from the main menu or
     the text editor (@/launch.lst).

 :!: You can run s16 programs if you have launched the 2qwk from gs/os but
     won't automatically return because I have no idea how to do that.

7.30    View text files         (T from main)

 This command lets you view files (see 4.3 for commands).

 :?:  This will view up to the first ~43k.

7.40    Re-read packet          (Y from main)

 This reprocesses the contents of the qwk directory. It's useful if you have
 changed it (see 2.21).


8.00    Appendices

8.01    Troubleshooting

 What needs to go in the qwk directory?

        messages.dat    Contains the messages.
        control.dat     BBS information, conference names.
        *.ndx           File position information for the messages.
        door.id         If you want to do offline configuration.

 :!: You will need the ndx files (see 6.20 if you mail host can't create them).

 In general:

  - Unpack all files to the same directory.

  - Make sure that you've installed the qfix patches on all programs that
    need them.

 Install don't work:

  - You are using a patched version of ProDOS-8 2.0.x, right?

  - Make sure that you have free space on the disk that you have installed
    the 2qwk on -- at least 50 blocks must be available.

 I get a 'control.dat not found' error message:

  - Make sure you set your qwk & rep directories correctly.

  - Use the Archiver to unpack the QWK data.

 The packet info comes up but no messages:

  - Make sure the mail door is sending the ndx files. If your mail door
    isn't capable of doing this you can use the 'make ndx files' utility.

  - Make sure your archiver is patched or the ndx files will have their
    named corrupted.  They should have names like "025.NDX".

 The rep packet don't get made:

  - Make sure you quit the program normally.

 I can't get no date:

  - Do not display your box of condoms during dinner at the DQ.

  - Stop doing Beavis & Butt-head imitations when asked a question.

  - Invest in Head & Shoulders, not Brylcreme.

  - Never introduce yourself as "that guy who got sick all over your friend
    Stacy".

8.02    Source code

 The source code for this program is available on request.

 :?: It's not that I've changed my mind on distribution of source, but it's
     not worth clogging up phone lines for something maybe 5 people will
     ever want to see.

8.03    Reaching the author or getting help

 Comments or suggestions can be directed towards:

        [e-mail]           (sometimes goofy)
        [e-mail]       (documentation & user help)